Skip to content

docs(releases): notes for 0.5.0 and draft 0.6.0#17

Merged
lesnik512 merged 1 commit into
mainfrom
docs/release-notes-0.5.0-and-0.6.0
Jun 9, 2026
Merged

docs(releases): notes for 0.5.0 and draft 0.6.0#17
lesnik512 merged 1 commit into
mainfrom
docs/release-notes-0.5.0-and-0.6.0

Conversation

@lesnik512

Copy link
Copy Markdown
Member

Summary

Catch-up release notes for two versions that were missed in the planning/releases/ per-version doc convention established in 0.4.0:

Pattern follows planning/releases/0.4.0.md and 0.3.1.md — title with tagline, opening paragraph (TL;DR + who cares), ## What landed, ## Why, ## Usage, ## Breaking changes, ## See also.

Test plan

  • mkdocs build --strict — N/A (release notes live under planning/, not docs/, so they're not part of the rendered site)
  • No code changes — just lint-ci and just test not affected

🤖 Generated with Claude Code

0.5.0 (already cut to PyPI as ffbf4d7 / 0.5.0): catches up the release
notes file — `tag --dry-run` CLI flag (PR #15) + docs site move to
modern-python.org subdomain (PR #14) + CI action pin bumps.

0.6.0 (tagged at efc5902, release pending): drafts the notes for the
upcoming release — `dry-run` input on action.yml + side-effect-free
action-smoke (PR #16). Pure action/CI change; no CLI source touched.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@lesnik512 lesnik512 merged commit 2d7ee91 into main Jun 9, 2026
6 checks passed
@lesnik512 lesnik512 deleted the docs/release-notes-0.5.0-and-0.6.0 branch June 9, 2026 14:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant